This was fixed in 2260fc5, although the commit will be rebased on top of master until jQuery 3.0.0 is released. @markelog did you want to wait until that happens?

@arthurvr what's the strategy you use for other content sites, like https://github.com/jquery/api.jquery.com/?

This was fixed in 2260fc5, although the commit will be rebased on top of master until jQuery 3.0.0 is released.

Yeah, exactly, commit hashes are not the same, because i added Closes ... comment, but they are the same, this pull will autoclose when that commit will be merged to master.

@arthurvr what's the strategy you use for other content sites, like https://github.com/jquery/api.jquery.com/?

We just close the PRs when we land them to the v3 branch, if that's where you're asking for.

When I merge a PR to the jquery-3 branch it gets auto-closed anyway, see e.g. #107. If we didn't want to get them closed, we'd have to be sure to always cherry-pick, even if a commit can be merged because it's already rebased.

Losing reference to the final version of the commit is not very nice, though. :/